Wireless communication diagnostics

ABSTRACT

A load control system may include devices for performing communications for controlling an amount of power provided to an electrical load. The devices may include load control devices that may communicate by transmitting digital messages. A user device having an adjustable wireless communication range may be used for discovering devices, configuring devices, and/or diagnosing devices in the load control system. The user device may detect whether devices are within an established wireless communication range of one another for performing communications. The user device may detect digital messages transmitted from a device and/or digital messages received at a device to determine whether the digital messages are correctly communicated in the load control system. The user device may provide an indication to a user indicating whether a digital message is correctly transmitted or received by a device in the load control system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No.61/920,504, filed Dec. 24, 2013, entitled WIRELESS COMMUNICATIONDIAGNOSTICS, the entire disclosure of which is hereby incorporated byreference.

BACKGROUND

A user environment, such as a residence or an office building forexample, may be configured with various types of load control systems. Alighting control system may be used to control the lighting loads in theuser environment. A motorized window treatment control system may beused to control the natural light provided to the user environment. Aheating, ventilation, and air-conditioning (HVAC) system may be used tocontrol the temperature in the user environment.

Each load control system may include various control devices, includingcontrol-source devices and control-target devices. The control-targetdevices may receive digital messages from one or more of thecontrol-source devices. The digital messages may include load controlmessages for controlling an electrical load. The control-target devicesmay be capable of directly controlling the electrical load. Thecontrol-source devices may be capable of indirectly controlling theelectrical load via the control-target device. Examples ofcontrol-target devices may include lighting control devices (e.g., adimmer switch, an electronic switch, a ballast, or a light-emittingdiode (LED) driver), a motorized window treatment, a temperature controldevice (e.g., a thermostat), a plug-in load control device, and/or thelike. Examples of control-source devices may include remote controldevices, occupancy sensors, daylight sensors, temperature sensors,shadow sensors, and/or the like. To enable a control-target device torecognize instructions received from a control-source device, thecontrol-target device and the control-source device may be associatedwith one another, such that the control-target device may recognize thedigital messages received from the control-source device.

FIG. 1A depicts a prior art user environment in which control-sourcedevices and control-target devices may be installed. As shown in FIG. 1,a user environment may include load control environments, e.g., rooms102, 104, and 106. Each of the rooms 102, 104, and 106 may includecontrol-target devices that may be capable of directly controlling anelectrical load. For example, rooms 102, 104, and 106 may includelighting control devices 112, 130, and 136. The lighting control devices112, 130, and 136 may be ballasts, LED drivers, dimmer switches, and/orthe like. Lighting control devices 112, 130, and 136 may be capable ofdirectly controlling an amount of power provided to lighting loads 114,132, and 138, respectively. Room 102 may include additionalcontrol-target devices, such as a motorized window treatment 116 fordirectly controlling the covering material 118 (e.g., via an electricalmotor), a plug-in load control device 126 for directly controlling afloor lamp 128, a desk lamp, or other electrical load that may beplugged into the plug-in load control device 126, and a temperaturecontrol device 124 (e.g., thermostat) for directly controlling an HVACsystem.

Rooms 102, 104, and 106 may include control-source devices capable ofindirectly controlling an electrical load by transmitting digitalmessages, such as load control messages, to a control-target device. Thecontrol-source devices in rooms 102, 104, and 106 may include remotecontrol devices 122, 134, and 140 that may send digital messages to thelighting control devices 112, 130, and 136, respectively. The lightingcontrol devices 112, 130, and 136 may control an amount of powerprovided to the lighting loads 114, 132, and 138, respectively, based onthe digital messages received from the remote control devices 122, 134,and 140. Room 102 may include additional control-source devices, such asan occupancy sensor 110, a daylight sensor 108, and a shadow sensor 120.The occupancy sensor 110 may send digital messages to a control-targetdevice based on an occupancy or vacancy condition (e.g., movement orlack of movement) that is sensed within its observable area. Thedaylight sensor 108 may send digital messages to a control-target devicebased on the detection of an amount of light within its observable area.The shadow sensor 120 may send digital messages to a control-targetdevice based on a measured level of light received from outside of theroom 102. For example, the shadow sensor 120 may detect when directsunlight is directly shining into the shadow sensor 120, is reflectedonto the shadow sensor 120, or is blocked by external means, such asclouds or a building, and may send a message indicating the measuredlight level.

When a user 142 attempts to use any of the control devices in the loadcontrol system shown in FIG. 1A, the control devices may operateimproperly or inefficiently. The improper or inefficient operation ofthe control devices may be due to an improper system configuration. Theload control system may be configured such that the control devices arenot optimally located within the load control system to properly receivedigital messages from other control devices. Additionally,communications between control devices may be improperly received, oreven lost, due to interference within the load control system. As shownin FIG. 1A, multiple control devices may be communicating digitalmessages within the same wireless space. Interference within thewireless space may result in lost digital messages and a lower level ofperformance within the load control system.

Current system configuration devices fail to provide a convenient way togather information for proper system configuration. FIG. 1B depicts aprior art system for gathering information and configuring the controldevices in a load control system based on the information gathered. Asshown in FIG. 1B, a user 144 may determine that a control device withinthe wireless communication system is operating improperly orinefficiently. The user 144 may be a contractor or other personexperienced in configuring control devices within the load controlsystem. The user 144 may use a wireless communication sniffing module148 to read wireless communications within the load control system. Thewireless communication sniffing module 148 may provide wirelesscommunication information to the user 144 via a laptop 146.

As shown in FIG. 1B, the wireless communication sniffing module 142 maybe able to read communications within the wireless range 148. Thewireless communication sniffing module 142 may, however, miss somedigital messages due to its proximity to some control devices. As somecontrol devices, such as the occupancy sensor 110, the lighting controldevice 112, the lighting control device 130, remote control 134, and/orremote control 140, may transmit and/or receive digital messages outsideof the wireless range 148, the lighting control device 130 may be unableto read these messages.

Additionally, for the digital messages that can be read by the wirelesscommunication sniffing module, the information that is read may beprovided in a format that may be unable to be understood by the user144. FIG. 2 is a diagram that illustrates an example of a graphical userinterface (GUI) 202 that may be provided to the user 144 on the laptop146 to indicate the digital messages 204 that may be read by thewireless communication sniffing module 142. The messages 204 may includean identifier of a source device from which the digital message wassent, an identifier of a target device to which the digital message wassent, a message identifier, and/or the like. As shown in FIG. 2, the GUI202 may provide the digital messages 204 in a constant stream of bitsthat may be difficult or unable to be understood by the user 144. Assuch, the user 144 may have to take the information gathered by thewireless communication sniffing module 148 to another destination tohave the digital messages parsed to properly troubleshoot the problemswith the wireless communications. The user 144 may then re-visit theload control environment shown in FIG. 1B to configure control devicestherein.

SUMMARY

A load control system may include control devices, such ascontrol-source devices and control-target devices, for controlling anamount of power provided to an electrical load. A control-target devicemay be capable of controlling the amount of power provided to theelectrical load based on digital messages received from a control-sourcedevice. The digital messages may include load control instructions oranother indication that causes the control-target device to determineload control instructions for controlling the electrical load.

The load control system may include a user device for providinginformation to a user for configuring the control devices in the loadcontrol system. The user device may detect whether control devices arewithin an established wireless communication range of one another. Theuser device may discover the control-target devices and/orcontrol-source devices. The established wireless communication range maybe adjusted to detect different devices. Once detected, the user devicemay send an identification message to the device that may cause thedevice to identify itself. The established wireless communication rangemay be adjusted to correspond to a transmit power of a control device todetect the devices within the wireless transmission range of the controldevice.

The user device may discover the control devices by broadcasting adiscovery message within the established range and receiving a responseto the discovery message from the control devices within the establishedwireless communication range. The discovery message may include anindication of a device type that may respond to the discovery message.The wireless communication range in which the discovery message may besent may be established based on a transmit power of the user device.The established range may be adjusted as the transmit power of the userdevice is adjusted. The established range may be determined bydisregarding any information received from a device outside of theestablished range.

The user device may detect whether a digital message is transmitted froma control device in the load control system. The user device may detecta digital message that may be sent from the control device through theestablished wireless communication range. The user device may parse theinformation in the digital message. The user device may identify thecontrol device to and/or from which the digital message may be sent. Thecontrol device may be identified by comparing a device identifier withinthe digital message with a device identifier stored within the userdevice. The device identifier may be obtained by the user device fromone or more devices in the load control system. The information withinthe digital message may be provided to the user in a manner that mayallow the user to determine whether one or more control devices may bereconfigured to improve the wireless communications within the loadcontrol system.

The user device may detect whether a digital message is received at acontrol device in the load control system. The user device may send adiscovery message to a control device within the established wirelesscommunication range. The discovery message may include an indication ofa device type that may respond to the discovery message and/or anindication of the type of information being requested by the userdevice. The discovery message may request the type of devices from whichthe control device may receive digital message and/or a timeframe inwhich the digital messages may have been received. The control devicemay respond to the discovery message by providing information about thecommunications received from other control devices within the wirelesscommunication system.

Communications between the user device and the devices within the loadcontrol system may be performed via a wireless communication module. Thewireless communication module may be capable of communicating with theuser device via a communication channel and with the load controldevices via another communication channel. The established wirelessrange of the user device may correspond to the transmit power of thewireless communication module. The wireless communication module mayadjust a transmit power to discover the control devices and/or digitalmessages within the established range.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A depicts an example prior art load control environment.

FIG. 1B depicts an example prior art load control environment thatincludes a prior art system for gathering information from controldevices in the load control environment.

FIG. 2 depicts an example of a prior art graphical user interface (GUI)that may be provided to a user to display digital messages read by awireless communication sniffing module.

FIGS. 3A, 3B, and 3C are example load control environments in whichinformation may be gathered from devices in the load controlenvironments.

FIG. 4 is a diagram depicting example ranges within which informationmay be gathered from devices in a load control environment.

FIGS. 5A-5D depict example messages that may be transmitted and/orreceived in a load control environment.

FIG. 6 is a diagram that depicts an example device for identifyingdevices and/or messages transmitted from devices in a load controlenvironment.

FIG. 7 is a simplified flow diagram for discovering control deviceswithin a wireless range.

FIG. 8 is a simplified flow diagram for discovering digital messagestransmitted in a load control environment and indicating the informationin the digital messages to a user.

FIGS. 9A and 9B depict example load control environments in which deviceinformation may be provided to a user device.

FIG. 10 depicts an example user device for identifying deviceinformation.

FIG. 11 is a simplified flow diagram for determining whether digitalmessages have been received at a device in a load control environment.

FIG. 12 illustrates example information that may be maintained at areceiving device in a load control system.

FIGS. 13A and 13B depict example GUIs that may be used to detect deviceswithin a wireless range.

FIGS. 14A and 14B are example GUIs that may be used to detect digitalmessages received by a device.

FIG. 15 is a block diagram illustrating an example user device.

FIG. 16 is a block diagram illustrating an example communication module.

FIG. 17 is a block diagram illustrating an example control device.

FIG. 18 is a block diagram illustrating an example load control device.

DETAILED DESCRIPTION

FIG. 3A depicts a representative environment for gathering informationfrom control devices in a load control system. The information may begathered for detecting problems in and/or configuring the load controlsystem. The load control environment may include control-source devicesand control-target devices. When a control-target device is associatedwith a control-source device, the control-target device may beresponsive to the control-source device. A device may be both acontrol-target and a control-source device. As shown in FIG. 3A, rooms302, 304, and 306 may be installed with one or more control-targetdevices. The control-target devices may be used for controlling (e.g.,directly controlling) the electrical loads within a room or building.Each control-target device may be controlled by a control-source device.Example control-target devices may include lighting control devices 312,330, and 336 (e.g., ballasts, LED drivers, dimmer switches, etc.) forcontrolling the amount of power provided to lighting loads 314, 332, and338, respectively, a motorized window treatment 316 having a motor driveunit (e.g., including a motor) for controlling the position of acovering material 318, a temperature control device 324 (e.g., athermostat) for controlling an HVAC system, and/or a plug-in loadcontrol device 326 for controlling a plug-in electrical load, such as afloor lamp 328, a table lamp or another electrical device that isplugged in to the plug-in load control device 326.

A control-source device may indirectly control the amount of powerprovided to an electrical load by transmitting digital messages to thecontrol-target device. The digital messages may include controlinstructions, such as load control instructions, or another indicationthat causes the control-target device to determine load controlinstructions for controlling an electrical load. Example control-sourcedevices may include a user device 344 (e.g., a mobile device), remotecontrol devices 322, 334, and 340, an occupancy sensor 310, and/or adaylight sensor 308. The user device 344 may include a wired or wirelessdevice. Examples of the user device 344 may include a wireless phone, atablet, a laptop, a personal digital assistant (PDA), or the like. Thecontrol-source devices may also include load control devices, such as adimmer switch, an electronic switch, or the like. The remote controldevices 322, 334, and 340 may be wireless devices capable of controllinga control-target device via wireless communications. The remote controldevices 322, 334, and 340 may be attached to the wall (e.g.,wall-mounted switch or wall-mounted dimmer) or detached from the wall.

The user device 344 may communicate with other devices via one or morecommunication modules, such as communication module 346. Thecommunication module 346 may be included in the user device 344, may beincluded in a load control device, or may be external to the user device344 and the load control devices, as shown in FIG. 3A. The user device344 may perform wired or wireless communications with communicationmodule 346. The communication module 346 may communicate with loadcontrol devices via wireless communications. Example wirelesscommunication channels, protocols, and/or technologies may use WI-FI®communication channels and/or protocols, ZIGBEE communication channelsand/or protocols, BLUETOOTH® communication channels and/or protocols, aproprietary communication protocol (such as the CLEAR CONNECT™protocol), near field communication (NFC) channels and/or protocols, orthe like. The communication module 346 may communicate with the userdevice 344 and one or more load control devices via differentcommunications channels. For example, the communication module 346 mayperform communications with the user device 344 via BLUETOOTH® acommunication channel and may communicate with one or more load controldevices via a WI-FI® communication channel or a communication channelhaving a proprietary communication protocol, such as CLEAR CONNECT™protocol.

The user device 344 may establish a wireless range 352 in which it maytransmit digital messages to and/or receive digital messages from otherdevices. The digital messages transmitted from the user device 344 maybe discovery messages that may be used to discover devices within theestablished range 352. The discovery message may be used to determinethe distance of devices that respond to the discovery message. Thediscovery message may be broadcast within the established range 352, ormay be directed to an individual device or group of devices within theestablished range 352.

The discovery message may be used to determine the transmission power ofa two-way communication device within the established range 352. Thediscovery message may be received by two-way communication devices thatmay respond to the discovery message by sending a response message. Thetwo-way communication devices may include control-source devices, suchas the daylight sensor 308, the occupancy sensor 310, the shadow sensor320, and/or the remote control device 322. The two-way communicationdevices may include control-target devices, such as the lighting controldevice 312, the motorized window treatment 316, the temperature controldevice 324, and/or the plug-in load control device 326.

The user device 344 may transmit the discovery message and receive aresponse to the discovery message from control devices capable ofperforming two-way communications within the established range 352. Theresponse message may include information identifying the control devicefrom which the response message is transmitted. The response message mayindicate the type of device responding (e.g., device-type identifier),an identifier (e.g., serial number) that may indicate the individualdevice, the link address for communicating with the device directly, thecommunication type (e.g., whether the device is a control-target device,a control-source device, or both), the wireless transmission range ofthe device, and/or other information about the control device. Uponreceipt of the response message, the user device 344 may determine thatthe control device from which the response message is received is withinthe established range 352. The received signal strength of the responsemessage may be used to determine the distance of the device from theuser device 344. The received signal strength may be indicated by areceived signal strength (RSS) value, a received signal strengthindicator (RSSI) value, or other measurement of the power present in areceived wireless signal.

The user device 344 may use the discovery message and the responsemessage received from control devices within the load control system todetermine whether the control devices are capable of properlycommunicating with other control devices within the system. As shown inFIG. 3B, the user 342 may position the user device 344 and/or thecommunication module 346 at, or near, one of the control devices in theload control system. While the user device 344 and/or the communicationmodule 346 are placed near the remote control device 322 in FIG. 3B, theuser device 344 and/or the communication module 346 may be placed at, ornear, any device in the load control system. The user 342 may set theestablished range 352 at, or within, the wireless communication range ofthe remote control device 322. The user device 344 may send a discoverymessage within the established range 352. When the user device 344receives a response message from a two-way communication control devicewithin the load control system, the user device 344 may determine thatthe control device from which the response message is received is withinthe wireless communication range of the remote control device 322 and iscapable of properly communicating with the remote control device 322. Ifa two-way communication control device does not respond to the discoverymessage, the control device may be out of range of the remote controldevice 322 or may be improperly configured.

The user device 344 may provide an indication to the user 342 of thecontrol devices from which it receives a response message. For example,the user device 344 may receive a response message from the lightingcontrol device 312, the motorized window treatment 316, and/or thebroadcaster 350 and may indicate to the user 342 that these controldevices are within the established range 352. The user device 344 mayidentify the type of device responding, the device identifier, the linkaddress for communicating with the device, the communication type (e.g.,whether the device is a control-target device, a control-source device,or both), the wireless transmission range of the device, and/or otherinformation about the control device from the response message and mayindicate such information to the user 342.

One-way communication control devices (e.g., transmit-only devices) mayprovide discovery information to the user device 344. The remote controldevice 322 and/or the occupancy sensor 310 may be examples of one-waycommunication control devices that may be unable to receive thediscovery message from the user device 344. To discover the remotecontrol device 322, the user 342 may actuate a button on the remotecontrol device 322 that may cause the remote control device 322 to senddiscovery information to the user device 344. To trigger thetransmission of discovery information at the occupancy sensor 310, theuser 342 may actuate a button on the occupancy sensor 310. The occupancysensor 310 may be equipped with a laser sensor that may identify a lasersignal transmitted from a laser (not shown) held by the user 342. Thelaser sensor may be used to cause any control device in a difficult toreach location to transmit digital messages. The detection of the lasersignal by the laser sensor at a one-way communication control device maytrigger the transmission of the discovery information. The discoveryinformation may indicate similar information as indicated by theresponse to the discovery message, such as the device type, the linkaddress, the device identifier (e.g., serial number), the transmissionrange of the device, the communication type (e.g., whether the device isa control-target device, a control-source device, or both), and/or otherinformation about the device, for example. While the remote controldevice 322 and the occupancy sensor 310 may be used as examples ofone-way communication control devices, any control device in the loadcontrol system may be a one-way or two-way communication control deviceand may similarly transmit discovery information.

The established range 352 may be adjusted to obtain information fromdifferent devices. As shown in FIG. 3C, the established range 352 may beadjusted to send digital messages, such as discovery messages, todifferent control devices in the load control system. The establishedrange 352 may be increased or decreased. In FIG. 3C, the establishedrange 354 may be increased in size from the size of the establishedrange 352 shown in FIG. 3B. The established range may be increased toallow the user device 344 to communicate with more control deviceswithin the load control system, or decreased to limit the number ofdevices with which the user device 344 may communicate. For example, theplug-in load control device 326 may be outside of the established range352 (shown in FIGS. 3A and 3B), but may be within the established range354 (shown in FIG. 3C) and may receive and/or respond to the discoverymessages transmitted within the established range 354.

The established range 352, 354 may also be used to determine whetherdevices in the load control system are improperly receiving digitalmessages. For example, the established range 354 may be used to transmitdigital messages to the lighting control device 336 that is in the room306. It may be determined that the lighting control device 336 isimproperly receiving digital messages from the remote control device 322in the room 302 if the lighting control device 336 responds to thediscovery message. If the lighting control device 336 is improperlyreceiving digital messages from the remote control device 322, thelocation of the remote control device 322 and/or the lighting controldevice 336 may be moved to a different location, the transmission powerof the remote control device 322 may be adjusted, or the lightingcontrol device 336 may be configured to ignore communications from theremote control device 322 (e.g., by disassociating the lighting controldevice 336 and the remote control device 322).

The user device 344 may use the received signal strength of a signalfrom devices to determine the distance of the devices from the userdevice 344 and/or whether devices are within a wireless communicationrange of one another. The received signal strength may be indicated byan RSS value, an RSSI value, or other measurement of the power presentin a received wireless signal. When the received signal strength is usedto measure the distance between two devices, the user device 344 may bepositioned at the location of one of the devices, or may not bepositioned at the location of either device. The user device 344 mayreceive a user indication (e.g., actuation of a button) that the user iswithin proximity to a device. The user device 344 may also, oralternatively, transmit a digital message to a two-way communicationdevice and use the response to determine that the user device 344 iswithin a predefined proximity to the device.

The received signal strength may be calculated at the user device 344upon receipt of a digital message from a one-way or two-waycommunication control device. The digital message may be received from atwo-way communication control device in response to a discovery message.The digital message may be otherwise triggered from a one-way or two-waycommunication control device, such as by pressing a button on thecontrol device or activating a sensor (e.g., a laser sensor) at thecontrol device, for example. The user device 344 and/or thecommunication module 346 may be positioned at a receiving location todetermine whether the control device from which the digital message istriggered is capable of transmitting messages to control devices at thelocation of the user device 344 and/or the communication module 346.

Once it is determined that two control devices are within wirelesscommunication range of one another, the control devices may be installedand/or configured for communication within the load communicationsystem. For example, a control-source device may be installed and may beassociated with a control-target device for performing communications.An association procedure may be performed by storing the deviceidentifier of the control-source device on the control-target deviceand/or by storing the device identifier of the control-target device onthe control-source device. The association may enable the control-sourcedevice to transmit digital messages to the control-target device and/orenable the control-target device to identify the digital messages fromthe control-source device. A similar association may be performedbetween any control devices in the load control system to enablecommunication between the control devices.

A control-target device may execute load control instructions receivedin the digital messages from an associated control-source device. Forexample, the remote control device 322 may instruct the lighting controldevice 312 to increase or decrease the lighting level of the lightingload 314, instruct the motorized window treatment 316 to raise or lowerthe covering material 318, instruct the plug-in load control device 326to raise or lower the lighting level of the floor lamp 328, and/orinstruct the temperature control device 324 to raise or lower thetemperature in one or more rooms. The occupancy sensor 310 may sendsimilar instructions to a control-target device based on the detectionof movement or occupancy within the room 302. The daylight sensor 308may send similar instructions to a control-target device based on thedetection of natural light within the room 302. The shadow sensor 320may send similar instructions to a control-target device based on ameasured level of light received from outside of the room 302.

The user device 344 may be used to determine whether digital messagesare properly being transmitted from a control device in the load controlsystem. The user device 344 and/or the communication module 346 maysniff (e.g., listen to the communications on) a communication linkbetween the control devices within the load control system to detectload control messages being transmitted from a control device. Forexample, the user device 344 may receive digital messages from acontrol-source device, such as the remote control device 322, to acontrol-target device, such as the lighting control device 312. Thedigital messages may be received when they are within the establishedrange 352, 354.

The user device 344 may detect that a digital message is improperlycommunicated and/or a control device is improperly configured based onthe information in the digital message. For example, the user device 344may detect that the remote control device 340 in the room 306 is sendingdigital messages to the lighting control device 312 in the room 302 forcontrolling the lighting load 314. The user device 344 may provide thisinformation and/or an indication to the user 342. From this informationit may be determined that the remote control device 340 in the room 306is improperly associated with the lighting control device 312 in theroom 302, rather than the lighting control device 336 in the same room.

The transmission of digital messages may be triggered by sending atriggering message to a control device within the established range 352,354. For example, the user device 344 may send a triggering message to acontrol-source device, which is a two-way communication device, to causethe control-source device to send a digital message to a control-targetdevice. For one-way communication devices, such as the remote controldevice 322 or the occupancy sensor 310 for example, the digital messagemay be triggered by pressing a button or pointing a laser at a sensor onthe device. The user device 344 may listen for the triggered digitalmessage from the control-source device. The user device 344 may detectthe triggered digital message based a source device identifier in thedigital message, a target device identifier in the digital message,information being transmitted in the message, and/or a proximity in timefrom transmission of the triggering message to the detection of thetriggered digital message.

The user device 344 and/or the communication module 346 may queryreceiving devices within the load control system to determine whetherdigital messages are properly being received. For example, the userdevice 344 may query a control-target device, such as the lightingcontrol device 312, to determine the messages that the control-targetdevice has received. The user device 344 may request the messagesreceived by the control-target device within a period of time (e.g.,messages received in the last 30 seconds) and/or the messages receivedfrom an identified device, such as an identified control-source device.The receiving device may store a log of the digital messages that it hasreceived and may use the message information in the log to providerequested information to the user device 344.

Based on the message information stored in a receiving device, the userdevice 344 may determine whether the receiving device is receiving theproper messages. If the receiving device is not receiving messagesintended for the receiving device, then the receiving device, or thetransmitting device from which the receiving device should be receivingthe messages, may be configured. For example, if the receiving device isnot receiving messages from a transmitting device, it may be determinedthat the receiving device is not associated with the transmitting deviceand the receiving device may then be associated with the transmittingdevice (e.g., using an association procedure). If the transmittingdevice is transmitting digital messages to the incorrect device, is nottransmitting the digital messages at a proper power level, or is nottransmitting the digital messages, the transmitting device may beconfigured to properly transmit the digital messages to the receivingdevice.

Control devices in the load control system may provide other informationto the user device 344. For example, the battery-powered control devicesmay report a low battery status to the user device 344. As the userdevice 344 may sniff messages being transmitted between control devicesand/or obtain message information from a receiving device, the lowbattery status information may be transmitted in digital messagesbetween control devices in the load control system and identified by theuser device 344. The digital messages may also provide an indication ofthe version of firmware being used by a device. The user device 344 mayidentify the firmware version and may be used to provide updates tocontrol devices in the load control system that are using an olderversion of firmware.

The user device 344 may communicate with a central processing device viawired or wireless communication. The central processing device may beon-site or at a remote location. The user device 344 may sendinformation to and/or receive information from the central processingdevice. The information may include device information discovered by theuser device 344 and/or a request for information from the centralprocessing device for configuring a control device in the load controlsystem. For example, the user device 344 may discover that a controldevice is using outdated firmware and may request the updated firmwarefrom the central processing device. The user device 344 may also receiveupdates for itself from the central processing device. The centralprocessing device may be a broadcaster 350. The broadcaster 350 maybroadcast information to one or more control devices within its wirelesscommunication range. The broadcaster 350 may receive information fromthe user device 344 and/or other devices in a load control system.

The user device 344 and/or the communication module 346 may communicatewith the load control devices via the broadcast controller 350. Thebroadcast controller 350 may include a wireless communication circuitcapable of broadcasting information to and/or receiving information fromone or more control devices within the wireless communication range ofthe broadcast controller 350. The user device 344 may be used todiscover and/or configure the broadcast controller 350. Examples of thebroadcast controller 350 are described in greater detail incommonly-assigned U.S. Non-Provisional patent application Ser. No.13/725,105, filed Dec. 21, 2012, entitled LOAD CONTROL SYSTEM HAVINGINDEPENDENTLY-CONTROLLED UNITS RESPONSIVE TO A BROADCAST CONTROLLER, theentire disclosure of which is hereby incorporated by reference.

Multiple communication modules, such as communication modules 346, 348,may be used for communicating with the user device 344. Thecommunication modules may be installed throughout the rooms 302, 304,and/or 306. The user device 344 may send a broadcast message to discovercommunication modules 346, 348. An identifier of the communicationmodules 346, 348 may be stored at the user device 344 for detectingcommunications from the communication modules 346, 348. An identifier ofthe user device 344 may be stored at the communication modules 346, 348for detecting communications from the user device 344.

While FIGS. 3A and 3B illustrate a single user device 344, multiple userdevices may be implemented to discover and/or configure devices in theload control system. Each of the user devices may be used by a differentuser. The user devices may be in communication with one another (e.g.,directly or via the Internet) to obtain information retrieved and/orstored at another user device. The user device 344 may discover when theestablished range 352, 354 overlaps with the established range ofanother user device and may indicate the overlap to the user 342. Theindication may be provided such that the user 342 may move to anotherlocation or adjust the established range 352, 354 to avoid discovering,and/or configuring devices in the same area as another user.

FIG. 4 is a diagram depicting example ranges that may be established forperforming discovery, configuration, and/or diagnostics for controldevices in a load control system. The load control system includes auser device 404 and a communication module 406. As shown in FIG. 4, anestablished range 408 may be adjustable. A user 402 may increase ordecrease the established range 408 (e.g., between −3 dBm and −9 dBm) todiscover, configure, and/or diagnose load control devices within alarger or smaller area. The established range 408 may be measured fromthe communication module 406, the user device 404, or the user 402. Forexample, the established range 408 may be determined based on thedistance that the communication module 406 and/or the user device 404are configured to transmit and/or receive information.

The established range 408 may be determined by adding to or subtractingfrom the distance that the communication module 406 and/or the userdevice 404 are configured to transmit and/or receive information. Todetermine the established range 408 from the user 402, the distancebetween the user 402 and the user device 404, or the distance betweenthe user 402 and the communication module 406, may be calculated. Thedistance from the user 402 may be added to or subtracted from thedistance that the user device 404 or the communication module 406 areconfigured to transmit and/or receive information. To determine theestablished range 408 from the user device 404, the distance between theuser device 404 and the communication module 406 may be added to orsubtracted from the distance that the communication module 406 isconfigured to transmit and/or receive information.

The range 408 may be established by adjusting the signal strength of thesignal transmitted by the communication module 406 or the user device404. For example, the signal strength may be increased or decreasedbetween −9 dBm and −3 dBm. The user device 404 may send digital messagesto and/or receive messages from load control devices within theestablished range 408. The user device 404 may determine the distance tocontrol devices within the established range based on the messagesreceived within, and/or from the control devices within, the establishedrange. The user device 404 may determine the information beingtransmitted by a control device based on the messages received withinthe established range 408. The user device 404 may determine theinformation being received by a control device based on the messagesreceived within, and/or from the control devices within, the establishedrange 408.

The user device 404 may establish the range 408 by disregardinginformation received from control devices outside of the range 408. Forexample, the communication module 406 or user device 404 may have astatic signal strength of −3 dBm and the established range 408 may be −9dBm. In this case, the user device 404 may send messages to and/orreceive messages from control devices within the −3 dBm area. The userdevice 404 may determine the distance of each control device based onthe received signal strength of the messages from the load controldevice. When the received signal strength of a control device is below apower threshold, the user device 404 may determine that the controldevice is outside of the established range 408 (e.g., between −9 dBm and−3 dBm) and may disregard any information received from the controldevice.

FIGS. 5A-5D depict examples of types of digital messages that may betransmitted and/or received by a user device. FIG. 5A depicts an exampleof a digital message 500. The digital message 500 may be a discoverymessage that may be sent from the user device to control devices withinan established range of the user device. The digital message 500 may beused to discover control devices, or information about control devices,within the established range. For example, the digital message 500 maybe a broadcast message that may be broadcast within the establishedrange and may be responded to by two-way communication control devicesthat receive the digital message 500. Information about a known controldevice (e.g., device type, transmission range of the device, messagesreceived at the device, etc.) may also be discovered using the digitalmessage 500.

The digital message 500 may include a source device identifier 502, atarget device identifier 504, a message identifier 506, a transmissionrange identifier 508, and/or a message 510. The source device identifier502 may include the device identifier of the user device. The targetdevice identifier 504 may include the device identifier of the intendedtarget device to which the digital message 500 may be transmitted. Thetarget device identifier 504 may be included in the digital message 500to discover information about a known control device. The messageidentifier 506 may include an identity of the digital message 500. Themessage identifier 506 may be iterated for each transmission from theuser device to indicate the next message transmitted by the user device.The transmission range identifier 508 may indicate a transmission rangewithin which a receiving device may be included in order to respond tothe digital message 500. For example, the transmission range identifier508 may be a received signal strength at which the digital message 500may be received at a receiving device and the receiving device maycompare the received signal strength with the transmission rangeidentifier to determine whether to respond. If the received signalstrength is above the threshold indicated by the transmission rangeidentifier, then the receiving device may respond. The message 510 mayinclude information about the user device, information about the loadcontrol system, and/or a request for information from the receivingdevice. The requested information from the receiving device may includea request for a response to the digital message 500 from the receivingdevice and/or the information to include in the response. The digitalmessage 500 may also include a message type and/or a link address forcommunicating with the user device directly.

FIG. 5B depicts an example of a digital message 520. The digital message520 may be a message that may be received at a user device in responseto a digital message, such as a discovery message, transmitted from theuser device. The digital message 520 may be otherwise triggered from acontrol device in the load control system, such as by actuation of abutton or sensing a laser signal at the control device. The digitalmessage 520 may include a source device identifier 522, a target deviceidentifier 524, a message identifier 526, a transmission rangeidentifier 528, and/or a message 530. The source device identifier 522may include the device identifier of the source device (e.g., a loadcontrol device) from which the digital message 520 may be sent. Thetarget device identifier 524 may include the device identifier of theuser device. The message identifier 526 may include an identity of thedigital message 520. The message identifier 526 may be iterated for eachtransmission from the source device to indicate the next messagetransmitted by the source device. The transmission range identifier 528may indicate a transmission range of the source device from which thedigital message 520 is sent. For example, the transmission rangeidentifier may be a transmission power of the source device from whichthe digital message may be sent. The message 530 may include informationabout the source device and/or information about the load controlsystem. The message 530 may include information included in response toa request from the user device. The digital message 520 may also includean identifier (e.g., serial number) that may indicate the model numberof the source device, a message type, a link address for communicatingwith the source device directly, and/or whether the source device is acontrol-target device or a control-source device.

FIG. 5C depicts an example of a digital message 540. The digital message540 may be sent from a source device to a target device within the loadcontrol system. For example, the digital message 540 may be sent from acontrol-source device to a control-target device for controlling anelectrical load. The digital message 540 may be sniffed by the userdevice on a communication link between the control-source device and thecontrol-target device. The digital message 540 may include a sourcedevice identifier 542, a target device identifier 544, a messageidentifier 546, a sequence number 548, and/or a message 550. The sourcedevice identifier 542 may include the device identifier of the sourcedevice (e.g., a control-source device) from which the digital message540 may be sent. The target device identifier 544 may include theintended target device (e.g., a control-target device) for the digitalmessage 540. The message identifier 546 may include an identity of thedigital message 540. The message identifier 546 may be iterated for eachtransmission from the source device to indicate the next messagetransmitted by the source device. The sequence number 548 may indicate aposition of the message 540 in a sequence of digital messagestransmitted from a source device. The sequence number 548 may beiterated for each message transmitted from the source device to thetarget device and/or having the same message type as other messages inthe sequence. For example, the sequence number 548 may be iterated aftereach transmission of an occupancy or vacancy condition at an occupancysensor to indicate to a receiving device the message number in a givensequence of messages for a single event (e.g., occupancy or vacancy).The message 550 may include information being sent from the sourcedevice to the target device. The message 550 may include load controlinformation from a control-source device to a control-target device. Thedigital message 540 may also include an identifier (e.g., serial number)that may indicate the model number of the source device, an identifier(e.g., serial number) that may indicate the model number of the targetdevice for receiving the digital message 540, a message type, and/orwhether the source device is a control-target device or a control-sourcedevice.

FIG. 5D depicts an example of a digital message 560. The digital message560 may be a triggering message for triggering transmission of messagesbetween devices within the load control system. For example, the digitalmessage 560 may be sent to trigger transmission of a digital messagefrom a control-source device to a control-target device. The digitalmessage 560 may include a source device identifier 562, a target deviceidentifier 564, a message identifier 566, and/or a message 568. Thesource device identifier 562 may include the device identifier of theuser device. The target device identifier 564 may include the deviceidentifier of the intended target device to which the digital message560 may be transmitted. The message identifier 566 may include anidentity of the digital message 560. The message identifier 566 may beiterated for each transmission from the user device. The message 568 mayinclude triggering information for triggering a message from thereceiving control device to another control device in the load controlsystem. The message 568 may indicate the message type or the type ofinformation to transmit in response to the digital message 560. Forexample, the message 568 may include information that may trigger anoccupancy sensor to transmit an occupancy condition. The triggereddigital message may be obtained by the user device (e.g., by sniffingthe communication or obtaining the message from another control devicethat received the message) and may be used to determine whether thetransmitting and/or the receiving device are operating correctly. Thetriggered digital message may be identified based on the time periodfrom which the digital message 560 was sent and when the triggereddigital message was transmitted or received.

While digital messages 500, 520, 540, and 560 in FIGS. 5A-5D may includea number of message fields, any number or combination of fields may beincluded in a digital message. For example, where a digital message is abroadcast message, the target device identifier may not be included inthe digital message. Each field in the digital messages 500, 520, 540,560 may include one or more bits in a bit sequence.

The user device may determine whether a digital message is beingproperly communicated from a control-source device to a control-targetdevice by comparing the target device identifier in a digital messagewith the device identifiers of known devices in the load control system.FIG. 6 depicts an example of a device table 602 that may be used by auser device 600 to identify control devices within the load controlsystem. The device table 602 may be stored at the user device 600 at thetime of manufacture, or upon later configuration. The device table 602may include a device type 604, a device identifier 606, and/orassociated devices 608 for control devices in the device table 602.

The user device 600 may compare the information in the device table 602with the information in received or sniffed digital messages todetermine whether the information in the digital messages is correctand/or whether the source device of the digital message is operatingcorrectly. The information in the digital messages may be correct if thedigital message is sent to the proper target device. The user device 600may compare the target device identifier in a digital message with thedevice identifiers 606 in the device table 602 to determine whether thetarget device of a digital message is a control device that is known tothe user device 600. The user device 600 may compare the deviceidentifiers known to be within an established range. The user device 600may compare the source device identifier in a digital message with thedevice types 604 to determine whether the source device is a knowndevice. The user device 600 may compare the target device identifier ina digital message from a source device with the associated devices 608of the source device to determine whether the source device istransmitting a message to an associated device. The user device 600 mayalso analyze the messages and/or message types to determine whether theproper information is being sent from the source device and/or to thetarget device. By comparing the device identifiers, the user device 600may determine that a source device is not communicating with the propertarget device or any target device within the established range (e.g.,transmitting digital messages with an incorrect target deviceidentifier) and may configure the source device to transmit to theproper target device (e.g., by associating the proper target device inthe established range with the source device). If the source device istransmitting improper information to a target device, the source devicemay be configured to transmit the proper information.

FIG. 7 is a simplified flow diagram of a method 700 for discoveringcontrol devices within a wireless range. The method 700 may begin at702. At 704, the user device may establish a wireless range fordiscovery of control devices. The established range may be adjustable tolarger or smaller ranges. The user device may detect control deviceswithin the established range at 706. For example, the user device maysend a discovery message within the established range and may receive aresponse message from two-way communication devices within theestablished range.

At 708, the user device may be used to determine whether a target deviceis within a wireless transmission range of a source device that mayattempt to communicate with the target device. For example, the userdevice may be placed at, or near, the location of the source device andmay transmit a digital message to the target device. To determinewhether the target device is capable of receiving a digital message fromthe source device, the established range may be at, or within, thewireless transmission range of the source device. The digital messagetransmitted from the user device may be configured similar to a digitalmessage transmitted from the source device. If the target deviceresponds, or the message is stored at the target device, it may bedetermined that the target device is capable of receiving communicationsfrom the source device.

The user device may also be used to determine whether the target deviceis within a wireless transmission range of a source device based ondigital messages received from the control devices. For example, theuser device may use the received signal strength of a digital messagereceived from the source device and the received signal strength of adigital message received from a target device and may determine thedistance to each device. If the distance between the devices is shorterthan the wireless communication range of the source device from which adigital message may be transmitted, the devices maybe within a wirelesscommunication range of one another. The wireless communication range ofthe source device may be communicated in the digital message received bythe user device, or the wireless communication range may be pre-storedon the user device. The method 700 may end at 710.

FIG. 8 is a simplified flow diagram of a method 800 for discoveringdigital messages transmitted in a load control environment andindicating the information in the digital messages to a user. The method800 may begin at 802. At 804, the user device may receive deviceidentifiers for control devices within a load control system. Thecontrol devices may be devices for transmitting and/or receiving digitalmessages within the load control system. The digital messages mayinclude load control instructions for controlling an electrical load.The user device may establish a wireless range at 806 for discoveringthe digital messages being transmitted. At 808, the user device maydiscover the digital messages within the established range of the userdevice. The user device may discover the digital messages by sniffingcommunication links between transmitting devices and receiving devices.

The user device may parse the information in the digital message at 810.For example, the user device may parse a source device identifier, atarget device identifier, a message identifier, a message type, asequence number, a message, and/or the like. At 812, the user device mayidentify the source device identifier and/or the target deviceidentifier. The user device may use the target device identifier, thesource device identifier, and/or other information in the digitalmessage to determine whether the digital message is being properlycommunicated and/or whether the digital message includes the properinformation for controlling devices in the load control system. Forexample, the user device may compare the source device identifier and/orthe target device identifier with a list of known devices in the loadcontrol system to determine whether the source device and/or the targetdevice are known devices in the load control system. The user device maydetermine whether the target device is associated with the source devicefor receiving digital messages from the source device. The user devicemay determine whether the message information (e.g., load controlinstructions) being transmitted to the target device is proper.

The user device may provide an indication to the user of the informationidentified in the digital message at 814. For example, the user devicemay display the source device identifier, the target device identifier,and/or the message being sent to the target device for the user todetermine whether the digital message includes the proper information.The user device may also independently identify whether the digitalmessage is being communicated correctly and/or whether the digitalmessage includes the proper information (e.g., load controlinstructions) for being communicated between the identified devices. Theuser device may provide an indication of whether or not the digitalmessage is being properly communicated and/or includes the properinformation. The method 800 may end at 816.

The list of other control devices in the load control system may bepre-stored on the user device, such as at the time of manufacture, thelist may be stored on the user device as an update, or the list may beobtained from other devices in the load control system. FIGS. 9A and 9Bdepict example load control environments in which device information maybe provided to a user device 344. As shown in FIG. 9A, the deviceinformation for the control devices in a load control system may bestored at a central controller 902. The central controller 902 may be aserver or other central processing entity, such as a broadcast controldevice. The central controller 902 may be within or outside of theestablished range 352. For example, the central controller 902 mayreside at a remote location and may be capable of communicating with theuser device 344 via the Internet.

The list of control devices in the load control system, and associatedinformation, may be stored in a device table 904. The device table 904may include a device type 906, a device identifier 908, and/orassociated devices 910 for the control devices listed in the devicetable 904. The device table 904 may also include an identifier (e.g.,serial number) that may indicate the model number of a control device, alink address for communicating with the device directly, and/or thecommunication type (e.g., whether the control device is a control-targetdevice, a control-source device, or both). The device table 904 mayinclude one-way communication devices, two-way communication devices,control-source devices, control-target devices, and/or other controldevices in a load control system.

The user device 344 may receive the list of the control devices in theload control system, or portions thereof, from the central controller902. The device table 904 may be provided in response to a request(e.g., a discovery message) from the user device 344. The user device344 may compare device identifiers of received messages against theinformation received from the central controller 902 to determinewhether the control devices in the load control system are operatingcorrectly.

As shown in FIG. 9B, the device information for the control devices in aload control system may be obtained from various control devices withinthe load control system. The user device 344 may obtain deviceidentifiers from the control devices themselves or the control deviceswith which they are associated. For example, the user device may obtainthe device information for the occupancy sensor 310 directly from theoccupancy sensor 310. The occupancy sensor 310 may have a device table914 stored thereon that may include its device identifier and/or otherinformation about the occupancy sensor. The device table 914 may alsoinclude an identifier (e.g., serial number) that may indicate the devicetype of the occupancy sensor 310, a link address for communicating withthe occupancy sensor 310 directly, and/or the communication type (e.g.,whether the device is a control-target device, a control-source device,or both).

Control devices in the load control system may also be able to provideinformation on associated control devices with which the control devicesare configured to communicate. For example, the lighting control device312 may store device information for itself, as well as the deviceinformation for associated control devices, such as the remote controldevice 322, the occupancy sensor 310, and/or the daylight sensor 308.The lighting control device 312 may have a device table 912 storedthereon that may include its device type 920, device identifier 922,and/or other information about the lighting control device 312. Thedevice table 912 may also include association information for thecontrol devices, an identifier (e.g., serial number) that may indicatethe model number of the control devices in the device table 912, a linkaddress for communicating with devices directly, and/or thecommunication type (e.g., whether the devices are control-targetdevices, control-source devices, or both). As the lighting controldevice 312 may be a control-target device, the lighting control device312 may store information for the control-source devices with which thelighting control device 312 is associated.

The user device 344 may also obtain device information from acontrol-source device, such as the remote control device 322. The remotecontrol device 322 may store device information for itself, as well asthe device information for associated control devices, such as theplug-in load control device 326, the lighting control device 312, thetemperature control device 324 (e.g., thermostat), and/or the motorizedwindow treatment 316. The remote control device 322 may have a devicetable 910 stored thereon that may include its device type 916, deviceidentifier 918, and/or other information about the remote control device322. The device table 910 may also include association information forthe control devices, an identifier (e.g., serial number) that mayindicate the model number of the control devices in the device table910, a link address for communicating with devices directly, and/or thecommunication type (e.g., whether the devices are control-targetdevices, control-source devices, or both). As the remote control device322 may be a control-source device, the remote control device 322 maystore information for the control-target devices with which the remotecontrol device 322 is associated.

The device tables 910, 912, 914 may be provided to the user device 344in response to a request (e.g., discovery message) from the user device344, upon actuation of a button on the control devices on which thedevice tables 910, 912, 914 are stored, upon triggering a laser sensoron the control devices on which the device tables 910, 912, 914 arestored, or another triggering mechanism. The user device 344 may obtainsimilar device information from other control devices in the loadcontrol system. The control devices from which the device information isobtained may be within the established range 352. The control deviceswithin the established range 352 may receive a digital message (e.g.,discovery message) from the user device 344 requesting the deviceinformation. In response, each control device may send the deviceinformation to the user device 344. Any device in the load controlsystem may provide similar device information to the user device 344 asdescribed herein.

FIG. 10 depicts an example user device 1002 for identifying deviceinformation. The user device 1002 may include a digital camera (notshown) for capturing digital images, a display 1004 for displaying thedigital images captured by the digital camera, a button 1008 for takingthe digital images with the digital camera, a zoom button 1006 forzooming in or out, and/or a photo button 1010 for accessing and/orviewing digital images. The user device 1002 may capture digital imagesof a control device, a device barcode 1014 or serial number, or devicepackaging 1012.

The user device 1002 may be used to retrieve device information based onthe digital image. The user device 1002 may identify a control device byretrieving information associated with the picture from internal storageor by sending the picture to a remote location to retrieve the deviceinformation. For example, the user device 1002 may send the picture to aremote server that may be used to lookup the device information based onthe digital image. The device information may be provided to the userdevice 1002 and may be stored on the user device for identifying digitalmessages and/or the devices to or from which the digital messages aretransmitted. The user device 1002 may include the device information ina device table stored on the user device 1002.

FIG. 11 is a simplified flow diagram depicting a method 1100 fordetermining whether digital messages have been received at a controldevice in a load control environment. As shown in FIG. 11, the method1100 may begin at 1102. At 1104, a user device may receive deviceidentifiers for transmitting devices and/or receiving devices in theload control system. The user device may establish a range at 1106 fordiscovery of receiving devices in the load control system. At 1108, theuser device may discover a receiving device within the establishedrange. The receiving device may be a control device that has receiveddigital messages from a transmitting device in the load control system.For example, the receiving device may be a control-target device forreceiving digital messages from a control-source device.

The user device may obtain information about the digital messagesreceived at the receiving device at 1110. The receiving device maymaintain a log of messages that have been received by the receivingdevice. The information about the digital messages stored at thereceiving device may be obtained by the user device at 1110 in responseto a triggering message transmitted from the user device. Theinformation about the digital messages stored at the receiving devicemay be otherwise obtained at 1110 in response to actuation of a buttonat the receiving device, triggering a sensor (e.g., a laser sensor) atthe receiving device, or another triggering operation.

At 1112, the user device may determine whether digital messages havebeen properly received by the receiving device. The user device maydetermine that the receiving device is not the proper device forreceiving the digital messages. For example, the user device maydetermine that the receiving device is not associated with thetransmitting device. The user device may determine that the information(e.g., load control information) in the received digital messages isimproper for controlling the receiving device. For example, theinformation in the digital messages received from an occupancy sensormay include an indication that the load control environment isunoccupied even though the load control environment is occupied. Thediscovered message information may be used to determine that thetransmitting device may be misconfigured.

The user device may determine, at 1112, that the receiving device hasnot received particular digital messages. Some digital messages may bepaired together, such that after receiving one of the messages anotherone of the paired messages should be received. The user device maydetermine that a digital message has not been properly received when oneof the paired messages has not been received at the receiving device.For example, the user device may identify that a lighting control devicehas received consecutive vacancy conditions from an occupancy sensorwithout receiving an occupancy condition. Occupancy conditions may besent by an occupancy sensor in a digital message at predefined intervalsover the period of time (e.g., in the form of a “heartbeat”) in which aspace may be occupied. A vacancy condition may be sent in a digitalmessage after occupancy has been detected and when an occupancy sensorfails to detect occupancy in a space over a predefined period of timesince the last occupancy condition. The user device may count the numberof consecutive digital messages received at a control device thatinclude vacancy conditions to determine the number of missed occupancyconditions. The user device may identify that the lighting controldevice has received consecutive button press indicators from a remotecontrol device, without receiving a button release indicator. The userdevice may identify that the lighting control device has received a stopindicator that indicates that a user has stopped pressing a button on aremote control device without receiving a raise indicator or a lowerindicator from a remote control device that indicates a user has presseda raise or lower button, respectively, for adjusting the intensity ofthe lighting load. The user device may determine that the receivingdevice has received a digital message triggered by a button beingpressed twice without receiving the digital message triggered when thesame button is pressed the first time. A device, such as a remotecontrol device, may be programmed to transmit a digital message upon asingle press of a button and transmit another message upon a secondpress of the button within a predefined period of time. A receivingdevice may receive the message transmitted on the first press of thebutton and may ignore this message if the second message is receivedwithin a predefined period of time from the receipt of the firstmessage. Similar determinations may be performed by a receiving deviceand may be provided to the user device. If digital messages are notbeing received at the intended receiving device, the user device maydetermine that the digital messages are being improperly communicated(e.g., distance between devices is too great, digital messages are beingdirected to another device, etc.), the transmitting device is improperlyconfigured (e.g., digital messages are not being generated ortransmitted), or the batteries are dead in the transmitting or thereceiving device.

At 1114, the user device may indicate to a user whether the digitalmessages have been properly received by a receiving device. The userdevice may provide the information retrieved from the receiving deviceand/or indicate digital messages that are being improperly received orare not being received. The method 1100 may end at 1116.

FIG. 12 depicts an example of the type of message information that maybe maintained at a receiving device in a load control system. Theinformation may be maintained in a table 1200. While the table 1200 maybe maintained by a control-target device and may include indicationsfrom an occupancy sensor, a remote control device, and a daylightsensor, a similar table may be maintained by any receiving device in aload control system capable of receiving digital messages. The table1200 may include a device type 1202 and/or a device identifier 1204 thatmay indicate a source device from which a digital message may bereceived. The table 1200 may include an event number 1206. The eventnumber 1206 may indicate one or more messages received from the samedevice for a single event. The event number 1206 may be iterated at thereceiving device to indicate a sequence of messages received by thetransmitting device for performing an identified event (e.g., occupancyor vacancy at an occupancy sensor, a button press at a remote controldevice, etc.). The receiving device and/or the user device may determinethat a digital message was generated and/or transmitted, but notreceived by the receiving device when the event number 1206 has beenskipped for a device. As shown in table 1200, the receiving device hasreceived a first, third, and fourth message in a sequence of messagesfrom an occupancy sensor. Based on the event number 1206 indicated inthe messages received from the occupancy sensor, the user device, and/orthe receiving device, may determine that the second message, or sequenceof messages, for an event in the message sequence (e.g., an occupancyevent) has not been properly received by the receiving device. This maybe indicated to the user by displaying the information in the table 1200or by indicating to the user explicitly that the second message in thesequence of messages from the occupancy sensor has not been received.

The table 1200 may include a message identifier 1208. The messageidentifier 1208 may be iterated at the transmitting device upon thetransmission of a message to track the messages transmitted by thedevice. The message identifier 1208 may be used to identify whether themessages have been properly generated at the transmitting device. As themessage identifiers 1208 include a sequence of messages from theoccupancy sensor that skip a message identifier number (e.g., 2346), itmay be determined that a message was properly generated at the occupancysensor, but was not received at the receiving device.

The table 1200 may include a list of received messages 1210. Thereceived messages 1210 may indicate the instructions that may be sent tothe receiving device. For example, the received messages 1210 mayinclude load control instructions and/or an indication of an input or acondition identified at a transmitting device (e.g., a control-sourcedevice) that may be used for executing load control instructions at thereceiving device (e.g., a control-target device). The received messages1210 may be used to identify whether the messages have been properlytransmitted from the transmitting device or received at the receivingdevice. As the received messages 1210 include a sequence of messagesfrom the occupancy sensor that indicate a vacancy condition, without anintervening occupancy condition, it may be determined that a message wasimproperly generated at the occupancy sensor or was not received at thereceiving device. While the occupancy sensor and the occupancy/vacancyevents are used as examples, similar analysis may be performed using theinformation in the table 1200 to determine whether digital messages areproperly being transmitted by or received from other load controldevices.

As described above, the table 1200 may be stored at a control-targetdevice that may be associated with an occupancy sensor, a remote controldevice, and/or a daylight sensor. The detected occupancy condition,instructions from the remote control device, and/or the lightingthreshold may be used to increase or decrease a lighting level at alighting control device, raise or lower a covering material using amotorized window treatment, and/or increase or decrease a temperature ina load control environment using a temperature control device.Increasing the lighting level may include increasing a dimming level orturning on a lighting load. Decreasing the lighting level may includedecreasing the dimming level or turning off the lighting load.

The table 1200 may include one or more of the fields illustrated in FIG.12, but is not limited to including such fields. For example, the table1200 may include an identifier (e.g., serial number) that may indicatethe model number of the source device from which a message is received,a message type, a link address for communicating with the source devicedirectly, and/or whether the device is a control-target device or acontrol-source device.

FIGS. 13A and 13B depict an example graphical user interface (GUI) 1302that may be used for discovering, configuring, and/or diagnosing devicesin a load control system. The GUI 1302 may include a discover button1304 for sending a discovery message, various criteria 1306, 1308, 1310for discovering devices, an identification button 1312 for causing adevice to identify itself, and/or discovered devices 1318, 1320, 1322,1324, 1326, 1328, 1330, 1332, 1334. The wireless communication range1306 of the user device may be established using a dropdown box or otherbutton (not shown) on the GUI 1302. The established range 1306 may beconfigurable based on the transmit power of the communication module orthe user device, or by disregarding messages received from outside ofthe established range 1306. For example, if the communication module iscapable of transmitting and/or receiving transmissions up to a distanceof twenty feet, the transmission and/or receiving range 1306 may beestablished incrementally between zero and twenty feet. The discoverybutton 1304 may be selected for transmitting a discovery message todevices within the established range 1306. The discovered devices withinthe established range 1306 may be displayed for identification,configuration, and/or diagnosis.

Other criteria may be used for discovering devices in the load controlsystem. The discovery message may include the other criteria and adevice that meets the other criteria may respond to the criteria. Inanother example, the discovered devices may be filtered by the othercriteria after sending a digital message to the user device. The othercriteria may include a device type 1308 and/or a device identifier 1310.The device identifier 1310 may be used to discover one or more deviceshaving a known identifier. The device type 1308 may include more generaldevice types, such as load control devices, control-source devices, orcontrol-target devices, or more specific device types, such as alighting control device, a motorized window treatment, a plug-in loadcontrol device, a remote control device, a temperature control device(e.g., thermostat), a daylight sensor, a shadow sensor, or an occupancysensor, for example. The device type 1308 may be limited to devicescapable of two-way communication, but the user device on which the GUI1302 may be displayed may be able to receive digital messages fromone-way communication devices for discovery.

The discovered devices may be displayed on the GUI 1302. The GUI 1302may indicate the device type for discovered devices and/or whether thedevices are control-source devices 1314 or control-target device 1316.As shown in FIG. 13A, the discovered devices may include the remotecontrol device 1318, the remote control device 1320, the daylight sensor1322, the occupancy sensor 1324, the dimmer switch 1326, the dimmerswitch 1328, the thermostat 1330, the plug-in load control device 1332,and/or the motorized window treatment 1334. While the displayed devicesinclude load control devices, the GUI 1302 may be used to discover otherdevices within the load control system, such as a broadcast controldevice or a central controller.

The GUI 1302 may be used to identify the discovered devices within aload control environment. For example, upon selection of a discovereddevice and/or an identification button on the GUI 1302, the user devicemay transmit an identification message to selected devices instructingthe devices to identify themselves to the user. The selected devices mayidentify themselves visually or audibly. The identification may beperformed on the discovered device, or a device with which thediscovered device is associated. For example, the remote control devices1318, 1320 may identify themselves by flashing an indicator light,providing an indication on a display, or providing an indication via anassociated control-target device. The daylight sensor 1322 and theoccupancy sensor 1324 may identify themselves by flashing an indicatorlight or providing an indication via an associated control-targetdevice. The dimmer switches 1326, 1328 may identify themselves byflashing a corresponding lighting fixture. The thermostat 1330 mayidentify itself by flashing an indicator light, providing a message onthe thermostat 1330 display, and/or providing an identification via theHVAC system controlled by the thermostat 1330. The thermostat 1330 mayprovide an indication via the HVAC system by turning the HVAC system onor off, increasing or decreasing the temperature of the HVAC system, orthe like. The plug-in load control device 1332 may identify itself via adisplay, an indicator light, or a device that is plugged into theplug-in load control device 1332. For example, the plug-in load controldevice 1332 may flash a lighting fixture of a lamp plugged into theplug-in load control device 1332, flash an indicator light on a deviceplugged into the plug-in load control device 1332, or the like. Themotorized window treatment 1334 may identify itself by moving thecorresponding covering material that it controls. For example, themotorized window treatment 1334 may jog the covering material up anddown a predefined distance, wiggle the covering material, or tilt thecovering material.

The GUI 1302 may indicate whether the discovered devices may be within atransmission range of the user device. As the established range 1306 maybe set, the user device may determine that the devices that respond tothe discovery message within the established range are within theestablished range from the user device. The GUI 1302 may also displaythe distance of discovered devices based on the received signal strengthof a signal on which a digital message may be received. For example, theGUI 1302 illustrates the distance of the remote control device 1320 andthe dimmer switch 1328 from the user device.

The GUI 1302 may indicate whether the discovered devices may be within atransmission range of one another. For example, a user may select abutton 1312 for identifying discovered devices that are within awireless communication range of one another. The user device may use thereceived signal power of each device to determine the distance of eachdevice from the user device. The user device may use the distance ofeach device from the user device to determine the distance between eachdevice (e.g., such as when the user device is located at a device). Theuser device may know the wireless communication range of each device andmay indicate to the user when the distance between the devices is at, orwithin, the wireless communication range of at least one of the devices.For example, the user device may determine whether the distance betweena control-source device 1314 and a control-target device 1316 is lessthan the wireless communication range of the control-source device 1314,such that the control-target device 1316 may receive load controlinstructions from the control-source device 1314.

As shown in FIG. 13B, the GUI 1302 may indicate the devices that arewithin a wireless communication range. In FIG. 13B, the occupancy sensor1324 and the dimmer switch 1326 are indicated as being within a wirelesscommunication range of one another. The occupancy sensor 1324 or thedimmer switch 1326 may be selected by a user prior to selecting thebutton 1312 and the user device may determine whether any devices arewithin the wireless transmission range of the selected devices. Theoccupancy sensor 1324 and the dimmer switch 1326 may be selected by auser prior to selecting the button 1312 and the user device maydetermine whether the selected devices are within the wirelesstransmission range of one another.

One or more fields associated with the discovered load control devicesmay be configured using the GUI 1302. For example, a load control devicemay be renamed using the GUI 1302. Control-source devices 1314 and/orcontrol-target devices 1316 may be renamed for better identification ordistinction. For example, the remote control device 1318 may be renamedto indicate the location of the remote control device or the location ofthe devices that the remote control device is configured to control,such as the “Living Room Remote Control.” Similarly, control-targetdevices 1316 may be renamed to indicate the location of thecontrol-target device and/or the load that is being controlled. Forexample, the dimmer switch 1326 may be renamed as the “Kitchen Dimmer.”

The load control devices may be selected to configure other fieldsassociated therewith, such as the device name, the device type, theassociated devices, the link address for communicating with the device,the communication type (e.g., whether the device is a control-targetdevice, a control-source device, or both), and/or other informationabout the device. The configuration information may be provided to adevice. For example, if the user device is used to determine that acontrol device is associated with the wrong device in a load controlsystem, the association may be changed using the GUI 1302 and may beprovided to the device.

The GUI 1302 may be used to create a common interface across loadcontrol devices and/or load control systems. The GUI 1302 may displaycontrol-source devices 1314 and/or control-target devices 1316 based onthe one or more parameters associated with the devices. The GUI 1302 maydisplay control-source devices 1314 and/or control-target devices 1316based on the location of the devices. For example, the GUI 1302 maydisplay control-source devices 1314 and/or control-target devices 1316for a room or a subset of rooms, a floor or a subset of floors, a zoneor subset of zones, or the like. The GUI 1302 may display control-sourcedevices 1314 and/or control-target devices 1316 based on a device type.For example, the GUI 1302 may display the control-source devices 1314 orthe control-target devices 1316 independently. The GUI 1302 may displaythe device types, such as the lighting control devices, motorized windowtreatment, thermostats, plug-in load control devices, etc.,independently.

FIGS. 14A and 14B depict an example GUI 1402 that may be used forobtaining message information from control devices in a load controlsystem. A user may select the message information to be obtained usingvarious criteria. Message information may be provided for a devicehaving an identifier 1406, a message having a message identifier 1408, aselected device type 1410, messages stored on devices within anestablished range 1412, and/or messages received by a control devicewithin an identified timeframe 1414. The device type 1410 may includemore general device types, such as load control devices, control-sourcedevices, or control-target devices, or more specific device types, suchas a lighting control device, a motorized window treatment, a plug-inload control device, a remote control device, a temperature controldevice (e.g., thermostat), a daylight sensor, a shadow sensor, or anoccupancy sensor, for example. The device type 1410 may be limited tocontrol devices capable of two-way communication for sending a discoverymessage to retrieve message information, but the user device on whichthe GUI 1402 may be displayed may be able to receive message informationfrom one-way communication devices and may display such information onthe user device.

The GUI 1402 may be used to identify control devices within a loadcontrol environment. The control devices may be identified to determinethe criteria for obtaining the message information from a device. Uponselection of an identification button 1416 on the GUI 1402, the userdevice may transmit an identification message to control devices havingthe selected criteria. The identification message may instruct thecontrol devices to identify themselves to the user. The selected devicesmay identify themselves visually or audibly. The identification may beperformed on the control device itself, or a control device with whichit is associated. For example, a control-source device may identifyitself via an associated control-target device.

The discovery button 1404 may be selected to discover messageinformation stored at a control device. Upon selection of the discoverybutton 1404, a discovery message may be sent to control devices withinthe established range 1412. The discovery message may include the otherselected criteria, such as the device identifier 1406, the messageidentifier 1408, the device type 1410, and/or the message timeframe1414. Two-way communication devices having the selected criteria mayrespond to the discovery message. The control devices may provide themessage information having the selected criteria. For example, when thedevice type 1410 is set to a lighting control device, the establishedrange 1412 is set to a five foot range, and the message timeframe 1414is set to a five minute timeframe, the lighting control devices within afive foot range that are capable of two-way communication may respondwith the stored messages that have been received in the last fiveminutes. Devices may provide message information upon receipt of anothertriggering event, such as actuation of a button on the control device orsensing a laser signal at the control device.

FIG. 14B depicts a GUI 1418 that may display the message information1420 that may be received from other control devices. The messageinformation 1420 may include a source device type 1422, a source deviceidentifier 1424, an event number 1426, a message identifier 1428, and/ora message 1430. The message information 1420 may also include anidentifier (e.g., serial number) that may indicate the model number ofthe source device, a message type, and/or whether the source device is acontrol-target device or a control-source device. The messageinformation 1420 may be used to determine whether a source device and atarget device are properly configured to perform communications in aload control system. For example, the message information 1420 indicatesthat the control device from which the message information 1420 wasobtained failed to receive the second message in a sequence of messagesfrom an occupancy sensor. The failed receipt of the digital message maybe due to an improper configuration at the source device and/or animproper configuration at the target device. The source device and/orthe target device may be configured to enable proper communication ofdigital messages between the control devices.

FIG. 15 is a block diagram illustrating an example user device 1500,which may be deployed as, for example, the user device 344 of the loadcontrol system of FIG. 3A. The user device 1500 may include a controlcircuit 1502 for controlling the functionality of the user device 1500.The control circuit 1502 may include one or more general purposeprocessors, special purpose processors, conventional processors, digitalsignal processors (DSPs), microprocessors, integrated circuits, aprogrammable logic device (PLD), application specific integratedcircuits (ASICs), or the like. The control circuit 1502 may performsignal coding, data processing, power control, input/output processing,or any other functionality that enables the user device 1500 to performas described herein. The control circuit 1502 may store information inand/or retrieve information from a memory 1506. The memory 1506 mayinclude a non-removable memory and/or a removable memory. Thenon-removable memory may include random-access memory (RAM), read-onlymemory (ROM), a hard disk, or any other type of non-removable memorystorage. The removable memory may include a subscriber identity module(SIM) card, a memory stick, a memory card, or any other type ofremovable memory.

The user device 1500 may include a communication circuit 1510 fortransmitting and/or receiving information. The communication circuit1510 may perform wireless or wired communications. The communicationcircuit 1510 may include the functionality of, or may be capable ofperforming communications with, a communication module. Thecommunication circuit 1510 may include an RF transceiver or othercircuit capable of performing wireless communications via an antenna.Communication circuit 1510 may be in communication with control circuit1502 for transmitting and/or receiving information.

The control circuit 1502 may be in communication with a display 1508(e.g., a visual display, such as an LED display) for providinginformation to a user. The display 1508 and the control circuit 1502 maybe in two-way communication, as the display 1508 may include a touchscreen module capable of receiving information from a user and providingsuch information to the control circuit 1502. The user device 1500 mayinclude another input source 1504, such as a keyboard or other buttons,from which user inputs may be received at the control circuit 1502.

Each of the modules within the user device 1500 may be powered by apower source 1512. The power source 1512 may include an AC power supplyor DC power supply, for example. The power source 1512 may generate asupply voltage V_(CC) for powering the modules within the user device1500.

FIG. 16 is a block diagram illustrating an example communication module1600, which may be deployed as, for example, the communication module346 of the load control system of FIG. 3A. The communication module 1600may include a control circuit 1602 for controlling the functionality ofthe communication module 1600. The control circuit 1602 may include oneor more general purpose processors, special purpose processors,conventional processors, digital signal processors (DSPs),microprocessors, integrated circuits, a programmable logic device (PLD),application specific integrated circuits (ASICs), or the like. Thecontrol circuit 1602 may perform signal coding, data processing, powercontrol, input/output processing, or any other functionality thatenables the communication module 1600 to perform as described herein.

The control circuit 1602 may store information in and/or retrieveinformation from a memory 1604. The memory 1604 may include anon-removable memory and/or a removable memory. The non-removable memorymay include random-access memory (RAM), read-only memory (ROM), a harddisk, or any other type of non-removable memory storage. The removablememory may include a subscriber identity module (SIM) card, a memorystick, a memory card, or any other type of removable memory.

The communication module 1600 may include a communication circuit 1606for transmitting and/or receiving information. The communication circuit1606 may perform wireless or wired communications. The communicationmodule 1600 may also, or alternatively, include a communication circuit1608 for transmitting and/or receiving information. The communicationcircuit 1608 may perform wireless or wired communications. Communicationcircuits 1606 and 1608 may be in communication with control circuit1602. The communication circuits 1606 and 1608 may include an RFtransceiver or other communication module capable of transmitting and/orreceiving wireless communications via an antenna. The communicationcircuit 1606 and communication circuit 1608 may be capable of performingcommunications via different communication channels. For example, thecommunication circuit 1606 may be capable of communicating with a userdevice via a wireless communication channel (e.g., a BLUETOOTH® or nearfield communication channel) and the communication circuit 1608 may becapable of communicating with load control devices or other devices in aload control system via another wireless communication channel (e.g.,WI-FI® or a proprietary communication channel, such as a communicationchannel using the CLEAR CONNECT™ protocol).

The control circuit 1602 may be in communication with an LED indicator1612 for providing indications to a user. Each of the modules within thecommunication module 1600 may be powered by a power source 1610. Thepower source 1610 may include an AC power supply or DC power supply, forexample. The power source 1610 may generate a supply voltage V_(CC) forpowering the modules within the communication module 1600.

FIG. 17 is a block diagram illustrating an example control device 1700.For example, the control device 1700 may be a control-source device. Thecontrol device 1700 may be a remote control device, an occupancy sensor,a daylight sensor, a temperature sensor, and/or the like. The controldevice 1700 may include a control circuit 1702 for controlling thefunctionality of the control device 1700. The control circuit 1702 maystore information in and/or retrieve information from a memory 1704. Thememory 1704 may include a non-removable memory and/or a removablememory.

The control device 1700 may include a communication circuit 1708 fortransmitting and/or receiving information. The communication circuit1708 may transmit and/or receive information via wired or wirelesscommunications. The communication circuit 1708 may include atransmitter, an RF transceiver, or other circuit capable of performingwired and/or wireless communications. The communication circuit 1708 maybe in communication with control circuit 1702 for transmitting and/orreceiving information.

The control circuit 1702 may also be in communication with an inputcircuit 1706. The input circuit 1706 may include a button or a sensorcircuit (e.g., an occupancy sensor circuit, a daylight sensor circuit,or a temperature sensor circuit) for receiving inputs that may be sentto a device for controlling an electrical load. The control circuit 1702may receive information from the input circuit 1706 (e.g., an indicationthat a button has been actuated or sensed information). The controlcircuit 1702 may retrieve load control instructions from the memory 1704based on the information received from the input circuit 1706. Thecontrol circuit 1702 may send the information received from the inputcircuit 1706 to another device via the communication circuit 1708. Eachof the modules within the control device 1700 may be powered by a powersource 1710.

FIG. 18 is a block diagram illustrating an example load control device1800. The load control device 1800 may be a control-target device forexample. The load control device 1800 may be a dimmer switch, anelectronic switch, an electronic ballast for lamps, an LED driver forLED light sources, a plug-in load control device, a temperature controldevice (e.g., a thermostat), a motor drive unit for a motorized windowtreatment, or other load control device. The load control device 1800may include a communication circuit 1802. The communication circuit 1802may include a receiver, an RF transceiver or other communication modulecapable of performing wired and/or wireless communications viacommunications link 1810.

The communication circuit 1802 may be in communication with a controlcircuit 1804. The control circuit 1804 may include one or more generalpurpose processors, special purpose processors, conventional processors,digital signal processors (DSPs), microprocessors, integrated circuits,a programmable logic device (PLD), application specific integratedcircuits (ASICs), or the like. The control circuit 1804 may performsignal coding, data processing, power control, input/output processing,or any other functionality that enables the load control device 1800 toperform as described herein.

The control circuit 1804 may store information in and/or retrieveinformation from a memory 1806. For example, the memory 1806 maymaintain a registry of associated load control devices and/or digitalmessage information. The memory 1806 may include a non-removable memoryand/or a removable memory. The load control circuit 1808 may receiveinstructions from the control circuit 1804 and may control theelectrical load 1816 based on the received instructions. The loadcontrol circuit 1808 may receive power via the hot connection 1812 andthe neutral connection 1814 and may provide an amount of power to theelectrical load 1816. The electrical load 1816 may include any type ofelectrical load.

Although features and elements are described herein in particularcombinations, each feature or element can be used alone or in anycombination with the other features and elements. The methods describedherein may be implemented in a computer program, software, or firmwareincorporated in a computer-readable medium for execution by a computeror processor. Examples of computer-readable media include electronicsignals (transmitted over wired or wireless connections) andcomputer-readable storage media. Examples of computer-readable storagemedia include, but are not limited to, a read only memory (ROM), arandom access memory (RAM), removable disks, and optical media such asCD-ROM disks, and digital versatile disks (DVDs).

The invention claimed is:
 1. A user device for determining whether amessage from a control-source device to a control-target device iscorrectly communicated, wherein the control-source device is configuredto indirectly control an amount of power provided to an electrical loadby sending messages to the control-target device, the user devicecomprising: a control circuit configured to: adjust a wireless range fortransmitting a first message to the control-source device; transmit thefirst message within the wireless range to the control-source device,wherein the first message comprises a transmission range identifier thatindicates a threshold; receive a second message from the control-sourcedevice, wherein the second message is received in a transmission fromthe control-source device to the control-target device, and wherein thetransmission of the second message from the control-source deviceindicates that a received signal strength of the first message at thecontrol-source device was greater than the threshold indicated by thetransmission range identifier; and determine, based on information inthe second message, whether the second message is correctly communicatedfrom the control-source device.
 2. The user device of claim 1, whereinthe control circuit is further configured to: determine, based on theinformation in the second message, a device identifier of thecontrol-source device; compare the device identifier of thecontrol-source device with a list of load control devices; and send anindication of whether the control-source device is included in the listof load control devices.
 3. The user device of claim 2, wherein thecontrol circuit is further configured to: determine, based on theinformation in the second message, a device identifier of thecontrol-target device; compare the device identifier of thecontrol-target device with the list of load control devices; and send anindication of whether the control-target device is included in the listof load control devices.
 4. The user device of claim 3, wherein thecontrol circuit is further configured to: compare the device identifierof the control-target device with one or more device identifiers forload control devices associated with the control-source device; and sendan indication of whether the control-source device is associated withthe control-target device for performing communication.
 5. The userdevice of claim 1, wherein the control circuit is further configured todetermine whether the control-target device received the second messagebased on information received from the control-target device in responseto a query to the control-target device.
 6. A method for determiningwhether a message from a control-source device to a control-targetdevice is correctly communicated, wherein the control-source device isconfigured to indirectly control an amount of power provided to anelectrical load by sending messages to the control-target device, themethod comprising: adjusting a wireless range for transmitting a firstmessage from a user device to the control-source device; transmitting,by the user device, the first message within the wireless range to thecontrol-source device, wherein the first message comprises atransmission range identifier that indicates a threshold; receiving, bythe control-source device, the first message; comparing, by thecontrol-source device, a received signal strength of the first messagewith the threshold indicated by the transmission range identifier;transmitting, by the control-source device, a second message to thecontrol-target device when the received signal strength of the firstmessage is above the threshold indicated by the transmission rangeidentifier; receiving, by the user device, the second message; anddetermining, at the user device based on information in the secondmessage, whether the second message is correctly communicated from thecontrol-source device.
 7. The method of claim 6, further comprising:determining, based on the information in the second message, a deviceidentifier of the control-source device; comparing the device identifierof the control-source device with a list of load control devices; andsending an indication of whether the control-source device is includedin the list of load control devices.
 8. The method of claim 7, furthercomprising: determining, based on the information in the second message,a device identifier of the control-target device; comparing the deviceidentifier of the control-target device with the list of load controldevices; and sending an indication of whether the control-target deviceis included in the list of load control devices.
 9. The method of claim8, further comprising: comparing the device identifier of thecontrol-target device with one or more device identifiers for loadcontrol devices associated with the control-source device; and sendingan indication of whether the control-source device is associated withthe control-target device for performing communication.
 10. The methodof claim 6, further comprising determining whether the control-targetdevice received the second message based on information received fromthe control-target device in response to a query to the control-targetdevice.